Pairable secure-access facilities

ABSTRACT

Systems and methods are provided for providing access to secure-access facilities based on pairing of the secure-access facilities with a user device such as a wearable device. A pairable secure-access facility may be a public storage facility or device such as a locker that includes communications circuitry for pairing with the user device. Once paired with the user device, the locker may operate a locking mechanism to lock the locker when the user device is away from the locker and to unlock the locker when the user device is in the vicinity of the locker. The locker may include a beacon for detecting and pairing with the user devices. Pairing the user device and the locker may include entering a locker identifier into the user device to ensure that the intended user device is paired with the intended locker.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/267,214, filed Feb. 4, 2019, now U.S. Pat. No. 10,460,543, which is acontinuation of U.S. Pat. No. 15,860,036, filed Jan. 2, 2018, now U.S.Pat. No. 10,198,885, which is a continuation of U.S. Pat. No.15,595,668, filed May 15, 2017, now U.S. Pat. No. 9,892,582, which is acontinuation of U.S. patent application Ser. No. 15/352,380, filed onNov. 15, 2016, now U.S. Pat. No. 9,652,918, which is a continuation ofU.S. patent application Ser. No. 14/557,331, filed Dec. 1, 2014, nowU.S. Pat. No. 9,542,784, each of which are hereby incorporated byreference in their entirety.

TECHNICAL FIELD

The present invention generally relates to secure public storagefacilities and, more particularly, to temporal pairing of a user devicewith a pairable secure-access facility.

BACKGROUND

Public locations such as train stations often provide lockers fortemporary individual use by a user. When a user wishes to gain access toa public locker, the user commonly has to obtain a physical key or acode in order to access the locker once it is locked, often followingpayment for a temporary rental of the locker. Payment for a lockertypically includes inserting coins or other currency into the locker, orpaying by credit card for the rental. However, physical keys and codescan be cumbersome and can easily be lost. It would therefore bedesirable to be able to provide improved secure storage for users inpublic places.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an illustrative networked system includinga secure-access facility, according to an embodiment.

FIG. 2 is a diagram of an illustrative locker having a beacon forpairing with a wearable user device, according to an embodiment.

FIG. 3 is a flowchart of an exemplary process for using a pairablesecure-access facility, according to an embodiment.

FIG. 4 is a diagram of an illustrative wearable device, implemented as awatch device, for pairing with a pairable secure-access facility,according to an embodiment.

FIG. 5 is a diagram of an illustrative wearable device, implemented as aring device, for pairing with a pairable secure-access facility,according to an embodiment.

FIG. 6 is a diagram of an illustrative wearable device, implemented asan eyeglass device, for pairing with a pairable secure-access facility,according to an embodiment.

FIG. 7 is a diagram of an illustrative wearable device for pairing witha pairable secure-access facility showing how the wearable device maygenerate a current that passes along the wearer's skin to the pairablesecure-access facility, according to an embodiment.

FIG. 8 is a flowchart of an exemplary process that may be performed by awearable device to pair with a pairable secure-access facility,according to an embodiment.

FIG. 9 is a flowchart of an exemplary process that may be performed by apairable secure-access facility to pair with wearable device of a user,according to an embodiment.

FIG. 10 is a block diagram of a computer system suitable forimplementing one or more components of FIG. 1, according to anembodiment.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that like reference numerals are used to identifylike elements illustrated in one or more of the figures, whereinshowings therein are for purposes of illustrating embodiments of thepresent disclosure and not for purposes of limiting the same.

DETAILED DESCRIPTION

Secure-access facilities such as secure storage facilities may beprovided to users in public places such as train stations, airports,recreational areas, campgrounds, parks, amusement parks, theme parks,truck stops, rest stops, sporting events, concerts, arenas, or otherareas. For example, travelers often desire a secure place to store theirluggage while awaiting transportation or while visiting a new location.A train station or an airport may include secure storage facilities suchas lockers that can be rented by the travelers for temporary securestorage of their luggage. The secure public storage may include a beaconor other communications circuitry for pairing the secure public storagewith a user device such as a wearable user device. The pairable securepublic storage may be locked and/or unlocked based on the pairing. Forexample, when a user rents a locker, the user may pair their wearabledevice with the locker. When the user removes the wearable device fromthe locker, the user device and the locker may lose communication andthe locker may lock. When the user returns to the locker and places thewearable device in the vicinity of the locker, the wearable device andthe locker may reestablish communications, and the locker may unlockand/or open. In this way, the user can be provided with an electronickey to the secure public storage without requiring the user to carry aphysical key or an additional device, and/or remember a code.

In some implementations, pairable secure storages such as a locker mayrequire the user to provide feedback information to confirm the pairing.For example, the locker may have a locker number and/or may generate aunique code such as PIN number and, in order to pair the user devicewith the locker, the user may be required to enter the locker numberand/or code into the user device to be communicated wirelessly to thelocker. Providing pairable secure storage with feedback from the userfor pairing in this way may help prevent third party access to thepairing or pairing with the wrong locker by helping to ensure that onlythe intended user device is paired with the intended locker that isproviding the locker number or code.

Entry of the code into the user device can be done via an on-screen pinpad (e.g., a virtual number pad with integers from 0-9), or throughother means such as tapping of the user device (e.g., a locker may beconfigured to detect 1-9 quick taps to enter each digit of the lockernumber and/or PIN) against the pairable secure-access facility.

In one embodiment, pairing of a pairable secure-access storage may becompleted using a short series of small electric currents sent along theuser's hand and/or arm from the locker that are detected by the wearabledevice. Data can be encoded in this series of currents which could besent back to the locker to verify that this wearable is the one whichshould be paired with.

Once paired, a locked secure storage facility may then require thepresence of the paired wearable device to unlock the locker. Prior topairing, when the locker is unused, a wearable device may be detected inthe vicinity of the locker and the locker may trigger a pairing processwith the wearable device.

Although secure storage facilities such as lockers are sometimesdiscussed herein as examples, this is merely illustrative. Othersecure-access facilities may also be pairable secure-access facilitiessuch as parking garages, truck stop showers, truck stop or airportrental beds or sleeping areas, mailboxes, restrooms or restroom stalls,or other secure areas that can be locked and/or unlocked based onpairing with a user device such as a wearable user device.

FIG. 1 is a block diagram of a networked system 100 suitable forimplementing processes for providing pairable secure-access facilitiessuch as pairable secure storage facilities, according to an embodiment.As shown, system 100 may comprise or implement a plurality of devices,servers, and/or software components that operate to perform variousmethodologies in accordance with the described embodiments. Exemplarydevices and servers may include device, stand-alone, andenterprise-class servers, operating an OS such as a MICROSOFT® OS, aUNIX® OS, a LINUX® OS, or other suitable device and/or server based OS.It can be appreciated that the devices and/or servers illustrated inFIG. 1 may be deployed in other ways and that the operations performedand/or the services provided by such devices and/or servers may becombined or separated for a given embodiment and may be performed by agreater number or fewer number of devices and/or servers. One or moredevices and/or servers may be operated and/or maintained by the same ordifferent entities.

System 100 may include one or more user devices such as user device 110.The user device may be a wearable device such as a watch, glasses, aring, a necklace, a glove, a nametag, a shirt, or other electronicdevice that can be worn on a portion of a person's body or clothing.

System 100 may also include a payment provider server 160 and a pairablesecure-access facility such as secure-access facility 180. Paymentprovider server 160, secure-access facility 180 and/or user device 110may be in communication over a network 170. User 102 (e.g., a visitor toa service location such as a traveler at a train station or a member ofa gym), may utilize their corresponding user device 110 to accesssecure-access facility 180. Secure-access facility 180 may be located ata merchant location or other service location such as a store, a hotel,a restaurant, a train station, a ship, a park, a campground, an airport,an entertainment location such as an arena, a stadium, a theater, anamusement park, a bank, or any other location at which a person maydesire to temporarily store one or more personal items or otherwiseaccess a secure area in public place.

For example, secure-access facility 180 may be a locker at a trainstation and user 102 may desire to temporarily store luggage in thelocker. The traveler may use user device 110 (e.g., a wearable device)to access locker 180 by pairing the user device with the locker. Inanother example, a truck driver may desire to access a private rentablesleeping and/or bathing area at a truck stop. The truck driver may useuser device 110 (e.g., a wearable device) to access the private sleepingor bathing area by pairing the user device with an access point of theprivate sleeping or bathing area.

As shown in FIG. 1, secure-access facility 180 may includecommunications equipment such as communications circuitry 188 and/or oneor more beacons such as wireless beacon 132. Communications circuitry188 and/or beacon 132 may include wireless communications equipment suchas short range wireless communications equipment or other wirelesscommunications equipment. Wireless communications equipment that may beincluded in a beacon such as beacon 132 may include Bluetooth Low Energy(BLE) beacon communications equipment, LTE Direct communicationsequipment, Near Field Communications (NFC) equipment, wireless localarea network equipment (e.g., WiFi based equipment), cellular networkequipment, global positioning system (GPS) equipment, combined cellularand GPS equipment, other radio or microwave based communicationsequipment, infrared communications equipment, and/or any combinationthereof. In some embodiments, beacon 132 may include relatively shortrange wireless communications equipment such as Bluetooth Low Energy(BLE) beacon communications equipment, LTE Direct communicationsequipment, and/or Near Field Communications (NFC) equipment andcommunications circuitry 188 may include relatively wider range wirelesscommunications circuitry such as wireless local area network equipment(e.g., WiFi based equipment), cellular network equipment, globalpositioning system (GPS) equipment, and/or combined cellular and GPSequipment. However, this is merely illustrative. In general, anysuitable arrangement of communications equipment may be provided insecure-access facility 180 for providing pairing and paired accesscapabilities with a user device.

As shown in FIG. 1, secure-access facility 180 may include a pairingmodule 182, a processor 183, a database 186, and a display 190. Pairingmodule 182 may be implemented as software running on processor 183and/or a dedicated hardware module for managing pairing operations forfacility 180 in cooperation with, for example, beacon 132. Pairingmodule 182 may cooperate with beacon 132 to emit a signal (e.g., a BLEcommunications signal and/or an NFC signal) that is receivable by a userdevice. The emitted signal may include an identifier for the beaconand/or the associated facility 180. A user device such as a wearableuser device may passively monitor for beacon communications such as BLEcommunications or other near field communications from, for example, apairable secure-access facility (e.g., a locker).

When, for example, a user device 110 detects a beacon signal from beacon132 and verifies the identifier as belonging to a locker, both the userdevice and the beacon in the locker may ramp up in power and establish aconnection. The connection may further enable the user device tocommunicate with one or more other servers such as payment providerserver 160. Beacon 132 may be connected to a networked device at thelocation of facility 180 or the beacon may include network functionalityto communicate with the payment provider server. The payment providerserver may be a server of a dedicated service provider for secure publicstorage (e.g., a locker space vendor) or may be general service provider(e.g., a train station or shopping mall) or a payment provider thatadditionally provides secure public storage at the service provider'slocations.

User device 110, locker 180, and payment provider server 160 may eachinclude one or more processors, memories, and other appropriatecomponents for executing instructions such as program code and/or datastored on one or more computer readable mediums to implement the variousapplications, data, and steps described herein. For example, suchinstructions may be stored in one or more computer readable media suchas memories or data storage devices internal and/or external to variouscomponents of system 100, and/or accessible over network 170.

User device 110 may be implemented using any appropriate hardware andsoftware such as hardware and software configured for wired and/orwireless communication with beacon 132, secure-access facility 180,and/or payment provider server 160. For example, in various embodiments,user device 110 may be implemented as a smart phone, a personal digitalassistant (PDA), a laptop computer, a tablet computer, a wearable devicesuch as a wristwatch or bracelet with appropriate computer hardwareresources, a ring with appropriate computer hardware resources,eyeglasses with appropriate computer hardware (e.g. GOOGLE GLASS®)and/or other types of computing devices capable of transmitting and/orreceiving data, such as an IPHONE® or an IPAD® from APPLE®. The userdevice may be managed or controlled by any suitable processing device.

As shown in FIG. 1, user device 110 may include a pairing module 112, aservice application 120, other applications 114, a database 116, adisplay 121, one or more processors such as processor 123, andcommunications circuitry 118 (sometimes referred to as a communicationsmodule). Pairing module 112, service application 120, and otherapplications 114 may correspond to and/or include processes, procedures,and/or applications executable by a hardware processor, for example, asoftware program and/or may be implemented as dedicated hardwaremodules.

Pairing module 112 may be used by user device 110 to establish aconnection between user device 110 and secure-access facility 180.Pairing module 112 may correspond to a specific software application orhardware module utilized by user device 110 to complete a pairing withsecure-access facility 180. The pairing may provide and/or verify anidentity of user device 110, including transmission of an identifier foruser device 110. Pairing module 112 may also correspond to anapplication available over the Internet for download from a serviceprovider server or payment provider server 160. Pairing module 112 mayutilize communications circuitry 118 to exchange short range wirelesscommunications with beacon 132 and/or communications circuitry 188 ofsecure-access facility 180 to complete a pairing process. Beacon 132 maybe configured to transmit an identifier such as a locker name, a lockerbrand, or a locker number reception and identification by user device110 and/or user 102.

Pairing application 112 may execute in the background of an operatingsystem of user device 110 and be configured to establish connections,using communication module 118, with one or more beacons 132 (e.g.,wireless beacons) of secure-access facility 180. The connection may beestablished with or without user input from user 102. For example,beacon 132 may broadcast a token, such as a universally uniqueidentifier (UUID), for reception by pairing module 112. Pairing module112 may utilize communication module 118 of the user device 110 toreceive the token from beacon 132. If pairing module 112 acknowledgesthe UUID as identifying facility 180, pairing module 112 may transmit anidentifier corresponding to user device 110 back to beacon 132. Pairingmodule 112 may utilize communication module 118 to communicate withbeacon 132 (e.g., over near field communication, Bluetooth, BluetoothLow Energy, radio, infrared, WiFi, cellular, GPS, combined cellular andGPS, microwave, a combination thereof, or other connection). Theidentifier from user device 110 may include, be transmitted with,concatenated with, or otherwise bundled with the identifier receivedfrom beacon 132.

Secure-access facility 180 may operate display 190 to provide the lockernumber or other unique identifier such as a PIN number or passcode touser 102. User 102 may enter the provided locker number or identifierinto user device 110 using, for example, input/output devices 127 (e.g.,a real or virtual keypad, a button, a switch, a touchscreen, etc.). Theentered number or identifier may be transmitted using communicationscircuitry 118 to beacon 132 or the user may use user device 110 todirectly enter the provided number or code to beacon 132 (e.g., bytapping user device 110 against beacon 132 so that the number or codemay be entered by proximity based communication between communicationscircuitry 118 and beacon 132).

Once a connection is established with beacon 132, user device 110 may bepaired with secure-access facility 180. The pairing process may thenassociate that user device 110 with the beacon 132 and/or facility 180.In such embodiments, pairing module 112 of user device 110 may utilizeshort range wireless communication with beacon 132 and/or communicationscircuitry 188, such as near field communication, Bluetooth, BluetoothLow Energy, radio, infrared, WiFi, cellular, GPS, combined cellular andGPS, microwave, a combination thereof, or other connection.

Pairing module 112 may utilize communication module 118 to passinformation such as user information to payment provider server 160,including information for processing a payment for temporary access tosecure-access facility 180 based on the pairing. User device 110 maycommunicate directly with payment provider server 160 through network170 and/or via secure-access facility 180 (e.g., using beacon 132 and/orcommunications circuitry 188). For example, user 102 may be providedwith the ability to access and pay for rental of a locker using a singlepairing operation between user device 110 and secure-access facility 180in which payment processing information is also exchanged with paymentprovider server 160 during, before and/or after the pairing operation.

User device 110 may include other applications 114 as may be desired inparticular embodiments to provide features to user device 110. Forexample, other applications 114 may include security applications forimplementing client-side security features, programmatic clientapplications for interfacing with appropriate application programminginterfaces (APIs) over network 170, or other types of applications.Other applications 114 may also include email, texting, voice and IMapplications that allow a user to send and receive emails, calls, texts,and other notifications through network 170. In various embodiments,other applications 114 may include financial applications, such asbanking, online payments, money transfer, mobile wallet, payment methodselection, and/or other applications. Other applications 114 may includebrowser and/or mapping applications where the functions are not providedby pairing module 112 and/or service application 120. Other applications114 may contain software programs, executable by a processor, includinga graphical user interface (GUI) configured to provide an interface tothe user.

User device 110 may further include memory such as database 116 whichmay include, for example, identifiers such as operating system registryentries, cookies associated with pairing module 112, service application120, and/or other applications 114, identifiers associated with hardwareof user device 110, or other appropriate identifiers, such asidentifiers used for payment/user/device authentication oridentification. Database 116 may include user device tokens and/orencryption keys, including a public key of secure-access facility 180for beacon 132. Database 116 may include identifying information fortokens enabling pairing module 112 to identify beacon 132 when receivinga corresponding token. In one embodiment, identifiers in database 116may be used to associate user device 110 with a particular user account164 maintained by payment provider server 160. Database 116 may furtherinclude online account access information.

User device 110 may include a communication module 118 adapted tocommunicate with beacon 132 and/or payment provider server 160. Invarious embodiments, communication module 118 may include a DSL (e.g.,Digital Subscriber Line) modem, a PSTN (Public Switched TelephoneNetwork) modem, an Ethernet device, a broadband device, a satellitedevice and/or various other types of wired and/or wireless networkcommunication devices including microwave, radio frequency, infrared,Bluetooth, BLE, WiFi, cellular, GPS, combined cellular and GPS,microwave, near field communication devices, and/or a combinationthereof. Communication module 118 may communicate directly with beacon132 without network 170 using short range wireless communications.

Beacon 132 may cooperate with pairing module 182 to pair the locker 180with the user device when the user device 110 is in proximity to beacon132. Secure-access facility 180 may be maintained, for example, by aservice location and/or a payment provider associated with paymentprovider server 160. Beacon 132 may be implemented using any appropriatehardware and software configured for wireless communication with userdevice 110. For example, in one embodiment, beacon 132 may beimplemented as a dongle device including a hardware processor and acommunication module, for example, connected to secure-access facility180. Beacon 132 may also act as a stand-alone device including aprocessor, communication module, and/or network interface componentconfigured to communicate with user device 110 and/or payment providerserver 160, (e.g., by communicating through LTE Direct). Although asingle beacon is described, a plurality of beacons may be included insecure-access facility 180. Beacon 132 may communicate with paymentprovider server 160 to enable payment provider server 160 to associate aparticular user 102 with a location at which a secure-access facility islocated.

Beacon 132 of FIG. 1 may include processes, procedures, and/orapplications executable by a hardware processor, for example, a softwareprogram, configured to interact with user devices 110. Beacon 132 mayinclude applications for transmitting requests to establish a connectionbetween a user device and beacon 132. Thus, beacon 132 may utilize a lowenergy short range wireless communication of beacon 132 to transmitrequests to establish a connection with user device 110, including anidentifier such as a Universally Unique Identifier (UUID). If userdevice 110 receives a request to establish the connection with beacon132 and respond with a device identifier (potentially including the UUIDand other information to effectuate a pairing of each device), beacon132 may ramp up in power and create a connection between user device 110and beacon 132.

Beacon 132 may transmit the request to establish the connection withuser device 110 as a short range communication (e.g. a BLE protocolcommunication) including a “wake up” process for pairing module 112 ofuser device 110 and/or a token for beacon 132 or secure-access facility180. In other embodiments, the request and/or connection may betransmitted using near field communication, radio communication,infrared communication, or Bluetooth communication, BLE communication,WiFi communication, cellular communication, GPS communication, microwavecommunication, and/or any suitable combination thereof.

After beacon 132 receives a device identifier, beacon 132 may determinethat user device 110 is at or in proximity to secure-access facility180. In one embodiment, beacon 132 may pass the user device identifierto payment provider server 160 to complete the pairing and paymentprocess and associate user device 110 with that facility 180. However,this is merely illustrative. In some embodiments, pairing of user device110 with secure-access facility 180 may be performed withoutcommunication with payment provider server 160. For example, the usermay pay separately for a locker rental and pairing operations may beperformed exclusively using communications between user device 110 andfacility 180.

Secure-access facility 180 may utilize communications circuitry 188 topass information to payment provider server 160 and/or beacon 132 mayutilize a network connection of beacon 132 through a communicationmodule of beacon 132 to communicate with payment provider server 160.Additionally, beacon 132 may keep a communication channel open betweenuser device 110 and payment provider server 160 for passing informationto and from the device.

Communications circuitry 188 may include a DSL (e.g., Digital SubscriberLine) modem, a PSTN (Public Switched Telephone Network) modem, anEthernet device, a broadband device, a satellite device and/or variousother types of wired and/or wireless network communication devicesincluding microwave, radio frequency, infrared, Bluetooth, BLE,cellular, GPS, combined cellular and GPS, microwave, near fieldcommunication devices, and/or any combination thereof. Communicationscircuitry 188 may communicate directly with user device 110 withoutnetwork 170 using short range wireless communications.

Secure-access facility 180 may be maintained by anyone or any entitythat establishes and/or maintains secure-access locations such aslockers in a location such as a location with services and/or productsoffered to users. Secure-access facility 180 may include a pairingmodule 182, input/output device 187 (e.g., a real or virtual keypad, oneor more buttons, switches or touchscreens), a database 186, a processor183, and a locking mechanism 189. Pairing module 182 may correspond toprocesses, procedures, and/or applications executable by a hardwareprocessor, for example, a software program.

Pairing module 182 may perform to processes to complete pairing withuser device 110. Thus, pairing module 182 may be configured to transmitand/or receive pairing requests from user devices such as user device110 and complete the pairing requests. In one embodiment, a pairingrequest may include log-in information for a user account 164 of paymentprovider server 160. Pairing may include verifying the accountinformation. However, in embodiments where a user account has not beenpreviously established by user 102, pairing module 182 may receive otherinformation for identifying user 102 or user device 110, such as usernames/identifiers, user device identifiers, or other information.

Additionally, pairing module 182 may unpair user device 110 when userdevice 110 leaves the proximity of beacon 132, when the user's paid timeruns out, or when the user removes their belongings from or otherwiseleaves the secure-access facility. Locking mechanism 189 may be amechanical lock, an electromagnetic lock, or other suitable structuresand/or circuitry operable to lock and unlock facility 180 (e.g., alockable opening to a secure internal cavity, room, or other space). Forexample, locking mechanism 189 may include a bolt or other physicallyactuatable member coupled to a motor or other mechanism for actuatingthe bolt to a locked or unlocked position. In another example, lockingmechanism 189 may include magnetic structures coupled to circuitry foralternately magnetizing or demagnetizing or more of the magneticstructures to secure or release an electromagnetic bond between themagnetic structures (e.g., opposing magnetic structures on a lockableopening such as a door and a frame of a locker or magnetic structureswithin a door of a locker that are operable to fix or release a doorhandle for opening the locker).

In various embodiments, secure-access facility 180 may include otherapplications and/or modules as may be desired in particular embodimentsto provide features to secure-access facility 180. For example, otherapplications may include security applications for implementingserver-side security features, programmatic server applications forinterfacing with appropriate application programming interfaces (APIs)over network 170, or other types of applications. Other applications maycontain software programs, executable by a processor, including agraphical user interface (GUI), configured to provide an interface to auser.

Secure-access facility 180 may include a database 186 which may include,for example, identifiers such as operating system registry entries,cookies associated with pairing module 182, identifiers associated withhardware of secure-access facility 180, or other appropriateidentifiers, such as identifiers used for pairing/payment/user/deviceauthentication or identification. Database 186 may store identifiersand/or user accounts of user 102, which may comprise an identifier foruser 102 and/or user device 110. In various embodiments, identifiers indatabase 186 may be used by a payment/credit provider, such as paymentprovider server 160, to associate user 102 with a particular accountmaintained by a payment provider server 160. For example, an identifierfor a payment account with a payment provider server 160 may be storedwith a user account and/or identifiers of users 102 in database 186. Inother embodiments, a user account stored in database 186 may include ashared identifier with the payment account with a payment providerserver 160. Identifiers stored in database 186 may be temporarily storedwhile a particular user owns access to the secure-access facility 180and may be erased or replaced when a subsequent user rents or purchasesaccess to the secure-access facility 180.

Payment provider server 160 may include a payment provider servermaintained, for example, by an online payment service provider, whichmay provide user account and payment services on behalf of user 102 andother users. In this regard, a payment provider server 160 includes oneor more processing applications, which may provide payment for itemsusing a user account with that payment provider server 160. In oneexample, payment provider server 160 may be provided by PAYPAL®, Inc. ofSan Jose, Calif., USA. Although payment provider server 160 is describedas separate from secure-access facility 180, payment provider server 160may be operated by a common entity with secure-access facility 180 or aseparate entity from secure-access facility 180. For example, a paymentprovider may provide secure-access facilities for use by users viadevice pairing at a location, a payment provider may provide paymentoperations for a third party provider of secure-access facilities foruse by users via device pairing at a location, or secure-accessfacilities for use by users via device pairing at a location may beprovided independent of any involvement of a payment provider.

Payment provider server 160 may include a transaction processing engine162, a database of user accounts 164, and a network interface component166. Transaction processing engine 162 may correspond to processes,procedures, and/or applications executable by a hardware processor, forexample, a software program or to dedicated hardware systems. In otherembodiments, payment provider server 160 may include additional ordifferent software or hardware as required.

Transaction processing engine 162 may be configured to receiveinformation from one or more user devices 110 and/or secure-accessfacility 180 for processing and completion of financial transactions.Transaction processing engine 162 may include one or more modules toprocess financial transactions between user devices 110 and/or serviceprovider server 140. Financial transactions may include financialinformation corresponding to user debit/credit card information,checking account information, a user account (e.g., payment account witha payment provider server 160), or other payment information.Transaction processing engine 162 may complete the financial transactionfor the purchase request by providing payment secure-access facility 180or an operator thereof. In various embodiments, transaction processingengine 162 may provide transaction histories, including receipts, touser device 110 in order to provide proof of purchase for temporaryaccess to secure-access facility 180.

Additionally, a payment provider server 160 includes user accounts 164.As previously discussed, user 102 may establish one or more useraccounts with a payment provider server 160. User accounts 164 mayinclude user information, such as name, address, birthdate,payment/funding information, travel information, additional userfinancial information, and/or other desired user data.

In various embodiments, payment provider server 160 may include at leastone network interface component 166 adapted to communicate with userdevice 110, and/or secure-access facility 180 over network 170. Invarious embodiments, network interface component 166 may comprise a DSL(e.g., Digital Subscriber Line) modem, a PSTN (Public Switched TelephoneNetwork) modem, an Ethernet device, a broadband device, a satellitedevice and/or various other types of wired and/or wireless networkcommunication devices including microwave, radio frequency (RF),infrared (IR), BLE, cellular, GPS, combined cellular and GPS, microwave,and/or near field communication devices, and/or any combination thereof.

Network 170 may be implemented as a single network or a combination ofmultiple networks. For example, in various embodiments, network 170 mayinclude the Internet or one or more intranets, landline networks,wireless networks, and/or other appropriate types of networks. Thus,network 170 may correspond to small scale communication networks, suchas a private or local area network, or a larger scale network, such as awide area network or the Internet, accessible by the various componentsof system 100.

FIG. 2 is a diagram of a plurality of exemplary secure-access facilities180 implemented as lockers in a locker bank 200. Locker bank 200 may belocated in any suitable location such as an airport, a train station, anamusement park, a campground, a hotel, a swimming pool facility or thelike. As shown in FIG. 2, each locker 180 may include a display 190 andcommunications circuitry such as a wireless beacon 132 and/or othercommunications circuitry such as NFC circuitry for communications 206between user device 110 and locker 180. Each locker 180 may include alockable opening such as a door 203 that provides access to an internalcavity 201 in which items such as personal belongings can be securelystored when door 203 is locked (e.g., using locking mechanism 189 ofFIG. 1, not shown in FIG. 2). It should be appreciated that otherlockable openings can be provided for a locker 180 or othersecure-access facility such as a gate, a lever arm, a turnstile, anotherhinged barrier, or other lockable opening.

When user device 110 is placed in the vicinity of a particular locker180 (e.g., within range of communications with beacon 132 such as within1 centimeters (cm), within 1 inch, within 4 cm, within 10 cm, or within100 cm), user device 110 and that locker 180 may be paired. As describedin further detail herein, during pairing operations, display 190 maydisplay a locker identifier such as a locker number or other numericalor alphanumeric code to the user of user device 110. While the lockeridentifier is displayed, the user may enter the locker identifier intouser device 110 (or directly into locker 180 using device 110). Thelocker identifier may be transmitted to locker 180 from user device 110so that locker 180 can identify which user device with which to pair.

Once paired, when the user removes user device 110 from the vicinity oflocker 180, locker 180 may actuate a locking mechanism to lock locker180. Access to that locker 180 may then require that the user returnuser device 110 to the vicinity of that locker 180. When the user device110 that has been paired with that locker 180 is returned to within thevicinity of that locker, the locker may actuate the locking mechanism tounlock the locker. For example, a pairing module of the locker may beconfigured to operate the mechanism to unlock the lockable opening whenthe user device is paired with the beacon and when the user device is incommunication with the beacon and/or to lock the lockable opening whenthe user device is paired with the beacon and when the user device isnot in communication with the beacon.

Locker 180 and/or user device 110 may store pairing information for theother so that the locker and the user device remain bonded and, when theuser device is returned to the vicinity of locker 180, communicationscan be reestablished for unlocking the locker. The pairing informationmay be stored for a limited time. For example, if the user rents alocker for three hours based on a pairing with their user device, thelocker may store pairing information for that user device for threehours. In this example, at the end of the three hours, the pairinginformation may be deleted or blocked so that the user would be requiredto pay for additional time and, in some scenarios, re-pair the userdevice and the locker to regain access to the locker.

Illustrative steps that may be performed by a user for using a pairablesecure-access facility such as a pairable secure public storage facilityare shown in FIG. 3.

At step 300, a user may pair a user device such as a wearable devicewith a pairable public storage. Pairing the wearable device with thepairable public storage may include placing the wearable device in thevicinity of the pairable public storage and entering a code providedfrom the pairable public storage into the wearable device. Pairing thewearable device with the pairable public storage may also includeproviding payment for temporary or permanent rental of the pairablepublic storage. Providing payment may include providing payment directlyto a point of sale device on the locker or the payment may beautomatically provided by a payment provider server in communicationwith the locker responsive to the pairing. For example, the user mayhave an account with the payment provider server and may have apre-authorization for locker rentals or other transactions with thepayment provider server. When the wearable user device is paired withthe locker, the user device or the locker may transmit a notification tothe payment provider server to process a payment from a user account ofthe user to an account of an operator of the pairable lockers. Invarious embodiments, the pairable locker maybe a specific one assignedto the user (such as when the user prepays or reserves a locker) orselectable from a group of lockers (such as at an amusement park, wherethe user can simply select one that is open).

At step 302, the user may access the pairable public secure storageusing the paired wearable device. For example, when the user returns toobtain one or more items from the locker, if the user is wearing orcarrying the previously paired user device, the user may simply open thelocker that has been unlocked based on the detected proximity of thewearable device when the user approaches.

FIGS. 4, 5, and 6 show exemplary implementations of a user deviceconfigured to be wearable and pairable with a pairable secure-accessfacility as described herein.

In the example of FIG. 4, user device 110 is implemented as anelectronic wristwatch having a housing 400 that is adapted to be wornaround a person's wrist. As shown in FIG. 4, a display 402 (e.g., animplementation of display 190 of FIG. 1) may be provided in housing 400.A virtual keypad 404 may be provided to the user with display 402. Thevirtual keypad may be used to enter a locker number or other code or PINprovided by a pairable secure-access facility for pairing of theelectronic watch with the pairable secure-access facility as describedherein.

In the example of FIG. 5, user device 110 is implemented as anelectronic ring having a housing 500 that is adapted to be worn around aperson's finger such as finger 502. As shown in FIG. 5, a display 504(e.g., an implementation of display 190 of FIG. 1) may be provided inhousing 500. Display 504 may be used provide instructions to the user(e.g., the display may present images or text such as “TAP”) indicatingthat the user should tap the electronic ring against a secure-accesspairable facility to enter a locker number or other code or PIN providedby the pairable secure-access facility for pairing of the electronicring with the pairable secure-access facility as described herein.

In the example of FIG. 6, user device 110 is implemented as electroniceyeglass having a frame 600 that is adapted to be worn on a person'sface. For example, frame 600 may include arms 604 that are adapted toextend over a person's ears. One or more lenses (e.g., transparent orsemitransparent plastic or glass) 602 may extend from frame 600 so thata wearer of the glasses looks through lenses 602. The glasses mayinclude a central portion 601 (e.g., a portion of the lenses or anadditional member mounted to or between the lenses) that is adapted torest on a person's nose to support lenses 602 in front of the user'seyes.

As shown in FIG. 6, lenses 602 may be implemented as a display (e.g., animplementation of display 190 of FIG. 1) for the eyeglasses. Forexample, text such as text 606 (e.g., “ENTER PAIR CODE NOW”) may beprojected onto or emitted from display pixels within lenses 602 suchthat a wearer of the eyeglasses can view and read the text. One or morebuttons such as button 608 may be provided with which the user can enterinformation such as a locker number or other code or PIN provided by apairable secure-access facility for pairing of the electronic eyeglasseswith the pairable secure-access facility as described herein. In anotherembodiment, the electronic eyeglasses may include a camera or other eyemonitoring equipment that can detect input from the user based on eyemovements and/or blinking.

As noted above, in one embodiment, a wearable user device maycommunicate directly with a pairing module on a pairable secure-accessfacility using electronic signals exchanged between the wearable userdevice and the pairable secure-access facility over, for example, thewearer's skin. FIG. 7 shows an exemplary implementation of user device110 for pairing with a pairable secure-access facility using electronicsignals transmitted over the wearer's skin. In the example of FIG. 7,user device 110 is implemented as an electronic wristwatch having ahousing 700 adapted to fit around a person's wrist.

As shown in FIG. 7, device 110 may include one or more electrodes 702.Electrodes 702 may be arranged to send and receive electrical signalssuch as signals 703 and 704 that travel along the skin of the user'shand 701. For example, when a user wishes to pair user device 110 with apairable secure-access facility 180, the user may contact a pairingmodule 706 on the pairable secure-access facility 180 with their skin(e.g., with a finger as shown in FIG. 7).

Pairing module 706 may include circuitry that transmits a signal 703such as a current that is received by electrodes 702 and processed by aprocessor (e.g., processor 183 and/or pairing module 112 of FIG. 1) ofthe user device. Signal 703 may include an identifier of that particularpairable secure-access facility 180. User device 110 may transmit asignal 704 that includes the identifier or other information based onthe identifier to circuitry of pairing module 706 using electrodes 702.Signals 703 and 704 may be exchanged in addition to other pairingcommunications between a beacon of the pairable secure-access facilityand communications circuitry of the user device and may be used inaddition to or in place of a PIN entry to verify pairing of the intendeduser device with the intended pairable secure-access facility.

Illustrative steps that may be performed by a user device such as awearable user device for obtaining access to a pairable secure-accessfacility based on pairing with the pairable secure-access facility areshown in FIG. 8.

At step 800, a pairable secure-access facility such as a pairable publicstorage device (e.g., a locker, a restroom, a bicycle locker or otherpairable secure-access facility as described herein) may be detectedwith a wearable user device. Detecting the pairable secure-accessfacility may include receiving, with communications circuitry of thewearable user device a signal transmitted by the pairable secure-accessfacility while the wearable user device is in proximity to the pairablesecure-access facility.

At step 802, pairing information may be provided from the wearable userdevice to the pairable public storage device. For example, the pairinginformation may include automatically transmitted information forpairing operations (e.g., a user device identifier) and may include astorage device identifier or PIN that has been entered into the wearableuser device by the user based on a display of the information by thepairable public storage device. As another example, the pairinginformation may include a storage device identifier or PIN that isentered via one or more taps with the wearable user device (e.g., asdescribed above in connection with FIG. 5) against the pairable publicstorage device. As another example, the pairing information may includea storage device identifier or PIN that is exchanged between thewearable user device and the pairable public storage device usingelectrical signals transmitted over the wearers skin (e.g., as describedabove in connection with FIG. 7).

At step 804, pairable public storage device access information may bestored on the wearable user device. The pairable public storage deviceaccess information may include encrypted or unencrypted informationgenerated based on the pairing of the wearable user device and thepairable public storage device such as an access code to be transmittedto the pairable public storage device when the pairable public storagedevice is again detected (e.g., when the user returns to the locker toopen the locker). In this way, the wearable user device and the pairablepublic storage device may remain bonded even when the wearable userdevice is separated from the pairable public storage device.

At step 806, the stored access information may be provided from thewearable user device to the pairable public storage device based on aproximity of the pairable public storage device. For example, when theuser returns to a locker that has been paired and is bonded with theiruser device, the wearable user device may again detect the pairablepublic storage device in the vicinity of the wearable user device.Responsive to the detection, the wearable user device may transmit(e.g., using BLE communications) the stored access information so thatthe user can access the pairable public storage device.

Illustrative steps that may be performed by a pairable secure-accessfacility for providing access to the pairable secure-access facilitybased on pairing with a user device such as a wearable user device areshown in FIG. 9.

At step 900, a user device such as a wearable user device may bedetected by a pairable secure-access facility such as a pairable publicstorage device (e.g., a locker, a restroom, a bicycle locker or otherpairable secure-access facility as described herein). Detecting thewearable user device may include receiving, with communicationscircuitry of the pairable secure-access facility signals transmitted bythe wearable user device while the wearable user device is in proximityto the pairable secure-access facility.

At step 902, pairing information may be displayed by the pairable publicstorage device. For example, a display of the pairable public storagedevice may be used to present a locker number or other unique identifierof the pairable public storage device to the wearer of the wearable userdevice.

At step 904, the pairing information that was displayed may be receivedfrom the wearable user device at the pairable public storage device. Forexample, the pairing information may be received following transmissionof the pairing information from the wearable user device as described,for example, in connection with step 802 of FIG. 8.

At step 906, the pairable public storage device may be paired with thewearable user device. Pairing the pairable public storage device withthe wearable user device may include generating and/or providingpairable public storage device access information to the wearable userdevice that can be stored by the user device and returned to thepairable public storage device when the user device is in the vicinityof the pairable public storage device.

While the user device stores the pairable public storage device accessinformation and while the pairable public storage device maintains thataccess information as an access key for granting access to the pairablepublic storage device, the wearable user device and the pairable publicstorage device may remain bonded so that, when the user device is in thevicinity (e.g., within communications range of communications circuitrysuch as NFC circuitry and/or BLE circuitry of the pairable publicstorage device) of the pairable public storage device, the pairablepublic storage device may be unlocked and when the user device is awayfrom the pairable public storage device (e.g., outside thecommunications range), the pairable public storage device may be locked.In another embodiment, while the pairable public storage device and userdevice are bonded, the user may be provided with options (e.g., on adisplay of the user device) for unlocking or locking the storage deviceeven while the user device is within the vicinity of the storage device.

At step 908, pairable public storage device access information may bereceived from the wearable user device at the pairable public storagedevice based on a proximity of the pairable public storage device andwearable user device. For example, when the user returns to a bondedlocker, the wearable user device may again detect the pairable publicstorage device in the vicinity of the wearable user device. Responsiveto the detection, the wearable user device may transmit (e.g., using BLEcommunications) the stored access information and the pairable publicstorage device may receive the transmitted information.

At step 910, the pairable public storage device may provide access tothe pairable public storage device responsive to the received accessinformation. For example, the pairable public storage device may receivethe access information from the user device, verify that the accessinformation is valid access information for that device and thatpairable public storage device, and operate a locking mechanism tounlock the pairable public storage device to provide the access.

Thus, a user may determine which user device the user wishes to pairwith the locker, based on various factors, including what will be mostconvenient for the user. For example, if the user is planning toexercise or swim, the user may select a ring as the pairing device. Inthat case, the user does not have to carry around a phone, watch, orother device that may be damaged or stolen while the user is engaged inan activity.

FIG. 10 is a block diagram of a computer system suitable forimplementing one or more components in FIG. 1, according to anembodiment. It should be appreciated that each of the devices utilizedby users and service providers may be implemented as computer system1000 in a manner as follows.

Computer system 1000 includes a bus 1002 or other communicationmechanism for communicating information data, signals, and informationbetween various components of computer system 1000. Components includean input/output (I/O) component 1004 that processes a user action, suchas selecting keys from a keypad/keyboard, selecting one or more buttons,image, or links, and/or moving one or more images, etc., and sends acorresponding signal to bus 1002. I/O component 1004 may also include anoutput component, such as a display 1011 and a cursor control 1013 (suchas a keyboard, keypad, mouse, etc.). An optional audio input/outputcomponent 1005 may also be included to allow a user to use voice forinputting information by converting audio signals. Audio I/O component1005 may allow the user to hear audio. A transceiver or networkinterface 1006 transmits and receives signals between computer system1000 and other devices, such as another user device, a merchant device,or a service provider server via network 170. In one embodiment, thetransmission is wireless, although other transmission mediums andmethods may also be suitable. One or more processors 1012, which can bea micro-controller, digital signal processor (DSP), or other processingcomponent, processes these various signals, such as for display oncomputer system 1000 or transmission to other devices via acommunication link 1018. Processor(s) 1012 may also control transmissionof information, such as cookies or IP addresses, to other devices.

Components of computer system 1000 also include a system memorycomponent 1014 (e.g., RAM), a static storage component 1016 (e.g., ROM),and/or a disk drive 1017. Computer system 1000 performs specificoperations by processor(s) 1012 and other components by executing one ormore sequences of instructions contained in system memory component1014. Logic may be encoded in a computer readable medium, which mayrefer to any medium that participates in providing instructions toprocessor(s) 1012 for execution. Such a medium may take many forms,including but not limited to, non-volatile media, volatile media, andtransmission media. In various embodiments, non-volatile media includesoptical or magnetic disks, volatile media includes dynamic memory, suchas system memory component 1014, and transmission media includes coaxialcables, copper wire, and fiber optics, including wires that comprise bus1002. In one embodiment, the logic is encoded in non-transitory computerreadable medium. A non-transitory computer-readable medium may includeinstructions which, in response to execution by a computer system, causethe computer system to perform some or all of one or more methods asdescribed herein. In one example, transmission media may take the formof acoustic or light waves, such as those generated during radio wave,optical, and infrared data communications.

Some common forms of computer readable media include, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EEPROM,FLASH-EEPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 1000. In various other embodiments of thepresent disclosure, a plurality of computer systems 1000 coupled bycommunication link 1018 to the network (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing disclosure is not intended to limit the present disclosureto the precise forms or particular fields of use disclosed. As such, itis contemplated that various alternate embodiments and/or modificationsto the present disclosure, whether explicitly described or impliedherein, are possible in light of the disclosure. Having thus describedembodiments of the present disclosure, persons of ordinary skill in theart will recognize that changes may be made in form and detail withoutdeparting from the scope of the present disclosure. Thus, the presentdisclosure is limited only by the claims.

What is claimed is:
 1. A method comprising: receiving, by an electronicdevice, information associated with a locker; transmitting, by theelectronic device based on the received information using a near-fieldcommunication (NFC) channel, data for pairing between the electronicdevice and the locker; receiving, using the NFC channel, a response fromthe paired locker, wherein the response relates to completion of thepairing; interactively providing, on the electronic device, a firstoption to unlock the paired locker or a second option to lock thelocker; receiving, by the electronic device, an interactive selectionincluding a least one of the first option or the second option; inresponse to detecting the interactive selection of the first option,causing, through the NFC channel, the paired locker to be unlocked; andin response to detecting the interactive selection of the second option,causing through the NFC channel, the paired locker to be locked.
 2. Themethod of claim 1, wherein the locker is associated with a PIN number.3. The method of claim 2, wherein the PIN number is used to pair theelectronic device with the locker.
 4. The method of claim 1, furthercomprising receiving a cost associated with a use of the locker.
 5. Themethod of claim 4, further comprising automatically providing paymentinformation for the cost.
 6. The method of claim 1, further comprisingcausing the locker to be locked in response to determining theelectronic device is past a predetermined distance of the locker.
 7. Themethod of claim 1, wherein causing the locker to be unlocked comprisessending, over a communication channel, a signal to unlock the lockerwhen the electronic device is within the predetermined distance of thelocker.
 8. The method of claim 1, further comprising storing informationabout the locker on the electronic device.
 9. The method of claim 8,further comprising deleting the information about the locker when a timeframe associated with a time limit of using the locker has expired. 10.The method of claim 1, further comprising displaying pairing informationon a display of the electronic device.
 11. The method of claim 1,wherein the electronic device is a wearable electronic device.
 12. Anelectronic device, comprising: at least one processor, and a memorystoring computer executable instructions that, when executed by the atleast one processor, perform operations, comprising: receiving, by anelectronic device information about a locker; storing the informationabout the locker; transmitting, by the electronic device based on thereceived information using a near-field communication (NFC) channel,data for paring between the electronic device and the locker; receiving,using the NFC channel, a response from the paired locker, wherein theresponse relates to completion of the pairing; interactively providing,on electronic device, an option to unlock the paired locker; receiving,by the electronic device, an interactive selection including the option;and in response to detecting the interactive selection of the option,causing, through the NFC channel, the paired locker to be unlocked. 13.The electronic device of claim 12, further comprising instructions forproviding, on a user interface of the electronic device, a second optionto lock the locker.
 14. The electronic device of claim 13, furthercomprising instructions for locking the locker in response to detectinga selection of the second option.
 15. The electronic device of claim 12,further comprising instructions for transmitting, over a communicationnetwork, information about the locker, the information including atleast one of an identifier associated with the locker or a costassociated with the locker.
 16. The electronic device of claim 15,further comprising instructions for automatically requesting paymentinformation from a payment service identified by the electronic device.17. The electronic device of claim 16, wherein the payment informationis associated with a cost for accessing locker.
 18. The electronicdevice of claim 12, further comprising instructions for receivingconfirmation of use of the locker.
 19. An electronic locking apparatus,the apparatus comprising: at least one processor; a locking mechanism; amemory storing computer-executable instructions that when executed bythe processor cause the electronic locking apparatus to: receive, by theelectronic locking apparatus using a near-field communication (NFC)channel, pairing information for pairing between the electronic lockingapparatus and an electronic device; transmitting, based on the receiveddata, access information of the electronic locking apparatus to thepaired electronic device; receiving, by the electronic locking apparatususing the NFC channel, access information; and responsive to thereceived access information from the electronic device, providing, bythe electronic locking apparatus, access to the electronic lockingapparatus operating the locking mechanism, wherein the operation of thelocking mechanism.
 20. The electronic apparatus of claim 19, thecomputer-executable instructions when executed further causing thesystem to: operating, by the electronic locking apparatus, the lockingmechanism for unlocking when the electronic device is within thepredetermined distance of the electronic locking apparatus.